| 1. | Changing log settings after deployment
在部署后更改日志设置 |
| 2. | For more information about changing log settings after deployment , see
有关在部署之后更改日志设置的更多信息，请参见 |
| 3. | Changes to this document since the proposed recommendation working draft are detailed in the change log
自建议推荐标准以来的修改已被详细记录在更改日志中。 |
| 4. | The change log table can then be used to determine the changes made to data units at any given time
这样就可以用变更记录表（ change log table ）确定在任何指定时间上对数据单元所做的更改。 |
| 5. | As stated earlier , triggers are an appropriate solution for automating the population of change data in a change log table
正如前面说过的，触发器是一种在变更记录表中自动填充更改数据的适当解决方案。 |
| 6. | Insert update delete triggers attached to a table can detect changes made to data units and record the changes in a change log table
附加到表上的插入/更新/删除触发器可以检测到对数据单元所做的更改，并在更改日志表中记录这些更改。 |
| 7. | In this section you specify the list of developers with proper ids , especially when you want the change log report and development activity report .
在此部分中指定开发人员名单带有正确的标识，当您希望获得更改日志change log报告和开发活动development activity报告时尤其要这么做。 |
| 8. | In this section you specify the list of developers with proper ids , especially when you want the change log report and development activity report . . ! - - - ! - project management section - ! - - - ! - details of the organization holding the project
在此部分中指定开发人员名单（带有正确的标识） ，当您希望获得更改日志（ change log ）报告和开发活动（ development activity ）报告时尤其要这么做。 |
